Point of sale payment system

ABSTRACT

A method for point of sale payments includes receiving, from a seller device over a network, payment information. The payment information is associated with payment code information in a database. The payment code information is then sent to the seller device over the network for posting at a service location. The payment code information is then captured by a payer device at the service location and transmitted over the network. The payment information is then retrieved from the database using the associated payment code information. The payment information is then sent to the payer device over the network. A payment confirmation is received from the payer device over the network and, in response, a payment from a payer account to a seller account is initiated and the payment information and an indication of the payment confirmation is sent to the seller device over the network.

CROSS REFERENCE TO RELATED APPLICATION

This patent application is a continuation of U.S. patent applicationSer. No. 13/338,509, filed Dec. 28, 2011, which claims priority to U.S.Provisional Patent Appl. Ser. No. 61/435,184, filed Jan. 21, 2011, allof which are incorporated by reference in their entirety.

BACKGROUND

1. Technical Field

Embodiments of the present disclosure generally relate to electronicpayments, and more particularly, to systems and methods for makingpayments at a point of sale.

2. Related Art

More and more consumers are purchasing items and services overelectronic networks such as, for example, the Internet. Consumersroutinely purchase products and services from merchants and individualsalike. The transactions may take place directly between a conventionalor on-line merchant or retailer and the consumer, and payment istypically made by entering credit card or other financial information.Transactions may also take place with the aid of an online or mobilepayment service provider such as, for example, PayPal, Inc. of San Jose,Calif. Such payment service providers can make transactions easier andsafer for the parties involved. Purchasing with the assistance of apayment service provider from the convenience of virtually anywhereusing a mobile device is one main reason why online and mobile purchasesare growing very quickly.

However, financial transactions such as those conducted at a point ofsale (POS) location generally require the provision by the customer of aphysical form of payment that typically includes cash, a check, or atransaction card such as a credit card, a debit card, or gift card. Suchconventional transactions are inefficient and introduce delays with thepurchase of products and/or services at the POS location. In someembodiments that include POS locations include, for example, parkingservices, transportation services, restaurants, retail stores, etc.paying with a physical form of payment may delay the completion of thetransaction as a result of the inability of the merchant to rapidlyprocess the transaction. For example, in a restaurant, a customer willgenerally may have to wave down or wait for a busy server in order toprovide a credit card for payment of the bill, then wait for the creditcard to be processed, then wait for a receipt, etc. These delays areundesirable for the customer and time-consuming for the merchant, andmay lead to decreased profits for the restaurant due to the resultinginefficiency in the turnover of tables.

In another embodiment, certain POS locations require “smart” POS devicesto process payments, such as those made using transaction cards. Forexample, POS devices may need to be secure in order to communicate andpossibly process sensitive financial information used to make thepayment, which makes the devices costly to implement and maintain forthe merchant. From the consumer side, such POS devices can beinconvenient, as they typically required the customer to make a paymentat a centralized POS device that is typically remote to the product orservice that is being purchased, such as, for example, when a consumerpurchases the use of a parking space, a bus/train seat, a movie seat,etc.

Thus, there is a need for an improved point of sale payment system.

SUMMARY

According to one embodiment, a method for point of sale paymentsincludes receiving payment information from a seller device operated bya seller. The seller may operate a service location (e.g., a parkinglot) that includes a plurality of payment locations (e.g., parkingspaces), and distinct payment information may be associated with each ofthe plurality of payment locations in the service location. Distinctpayment information is then associated with distinct payment codeinformation in a database, and the payment code information is sent tothe seller device. The seller may then provide the distinct payment codeinformation at each respective and distinct payment location as a signor other physical representation of the payment code information. Apayer wishing to make a payment to use the payment location may then usea payer device to capture the payment code information (e.g., bycapturing an image of the payment code information) and transmit thepayment code information such that it may be used to retrieve itsassociated payment information. That associated payment information maythen be transmitted back to the payer device such that the payer mayreview it and provide a payment confirmation indicating that the payerwould like to make a payment to the seller for the payment location.Upon receipt of the payment confirmation, the payment, information andan indication of the payment confirmation may be sent to the sellerdevice to confirm to the seller that the payer has paid for the paymentlocation.

As a result, the seller need only provide payment code information at aPOS location in a relatively inexpensive physical sign, rather thanimplementing computing devices and/or other ‘smart’ point of salesystems. The payer may use their payer device (e.g., a smart phone thata majority of potential payers typically carry with them a majority ofthe time) to pay for the use of the payment location simply by capturingand sending the payment code information and confirming a payment. Insome embodiments, the seller may use a seller device that receivesindications of payment confirmations and their associated paymentinformation in order to monitor whether payment locations in the servicelocation have been paid for.

These and other features and advantages of the present disclosure willbe more readily apparent from the detailed description of theembodiments set forth below taken in conjunction with the accompanyingfigures.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a flow chart illustrating an embodiment of a method for pointof sale payments;

FIG. 2 is a schematic view illustrating an embodiment of a servicelocation;

FIG. 3 is a screenshot illustrating an embodiment of a payment codeinformation provision page;

FIG. 4 is a perspective view illustrating an embodiment of a usercapturing an image of payment code information located adjacent apayment location in the service location of FIG. 2;

FIG. 5 is a screenshot illustrating an embodiment of the payment codeinformation of FIG. 4 being captured using the payment code informationprovision page of FIG. 3;

FIG. 6 is a screenshot illustrating an embodiment of payment codeinformation of FIG. 4 being captured using the payment code informationprovision page of FIG. 3;

FIG. 7 is a screenshot illustrating an embodiment of payment informationbeing displayed on a payer device;

FIG. 8 is a screenshot illustrating an embodiment of a paymentinformation being displayed on a seller device;

FIG. 9 is a schematic view illustrating an embodiment of a servicelocation;

FIG. 10 is a screenshot illustrating an embodiment of a payment codeinformation provision page;

FIG. 11 is a perspective view illustrating an embodiment of a usercapturing an image of payment code information located adjacent apayment location in the service location of FIG. 9;

FIG. 12 is a screenshot illustrating an embodiment of paymentinformation being displayed on a payer device;

FIG. 13 is a screenshot illustrating an embodiment of paymentinformation being displayed on a seller device;

FIG. 14 is a schematic view illustrating an embodiment of a networkedsystem;

FIG. 15 is a perspective view illustrating an embodiment of a payerdevice;

FIG. 16 is a schematic view illustrating an embodiment of a computersystem; and

FIG. 17 is a schematic view illustrating an embodiment of a sellerdevice, a payment service provider device, a funding account providerdevice, a POS payment service provider device, and/or combinationsthereof.

Embodiments of the present disclosure and their advantages are bestunderstood by referring to the detailed description that follows. Itshould be appreciated that like reference numerals are used to identifylike elements illustrated in one or more of the figures, whereinshowings therein are for purposes of illustrating embodiments of thepresent disclosure and not for purposes of limiting the same.

DETAILED DESCRIPTION

The present disclosure provides a system and method for making point ofsale payments. In an embodiment, a seller operates a service locationincluding a plurality of payment locations. For each payment location inthe service location, payment information for that payment location maybe associated with payment code information in a payment informationdatabase, and the payment code information may be provided to the sellerfor provision adjacent its associated payment location in the servicelocation. A payer includes a payer device having a payment application.In an embodiment, the payment application allows the payer to use acamera on the payer device to capture an image of the payment codeinformation that is provided adjacent the payment location. The paymentcode information is sent to a payment information engine such thatpayment information associated with the payment code information may beretrieved and returned, over the network, to the payer device. The payermay then provide a payment confirmation so that a payment may beinitiated from a payer account of a payer to a seller account of theseller, which then causes funds to be transferred from a funding accountof the payer to the seller account.

Referring now to FIGS. 1 and 2, a method 100 for point of sale (POS)payments is illustrated. A few embodiments of the POS payment system areprovided below that include service locations having payment locations,such as the parking lot (with parking spaces) and train (with seats)described below. However, these embodiments are not meant to belimiting, and one of skill in the art will recognize that a variety ofother POS payment scenarios will fall within the scope of the system andmethod described herein.

The method 100 begins at block 102 where payment information is receivedfrom a seller. In an embodiment, the POS payment system includes one ormore payment information databases in which distinct payment information(e.g., for each payment location or other service provided in the POSpayment system) is associated with distinct payment code information.For example, referring to FIG. 2, a seller may operate a servicelocation 200 that, in the illustrated embodiment, includes a parkinglot. The service location 200 includes a plurality of payment locations202 that, in the illustrated embodiment, include parking spaces. In theembodiment illustrated in FIG. 2, a plurality of payers have paid forrespective payment locations 202 in order to use the payment locations202 to park their cars 204. In one example, at block 102, the seller mayuse a seller device to send distinct payment information that isassociated with each distinct payment location 202 in the servicelocation 200 to a payment information engine, described in detail below.In another example, an POS payment system provider may include a paymentinformation engine that accepts payment information for paymentlocations in service locations from a plurality of different sellers. Inthis example, payment information may include additional informationthat is not directly related to the payment locations such as, forexample, seller information about the seller. In another example, apayment service provider device that is located remote from the POSlocation and that is distinct from the seller may provide paymentservices such that the payer may make a payment to the seller withoutany direct exchange of information between the payer and the seller.

The method 100 then proceeds to block 104 where the payment informationfor each payment location is associated with distinct payment codeinformation in the payment information databases. As described infurther detail below, the distinct payment code information may include,for example, a distinct alphanumeric character string and/or otheridentifier known in the art that may be associated with paymentinformation for each payment location in the payment informationdatabase. Thus, in one embodiment, the POS payment system may beseller-specific in that only a single seller's payment locations intheir service location are available to be paid for using the POSpayment system. In another embodiment, the POS payment system mayprovide for the payment for payment locations in a variety of servicelocations from a variety of different sellers who ‘register’ theirservice locations/payment locations with the POS payment system providersuch that payment code information may be associated with each of theirpayment locations. In embodiments where a variety of different sellersprovide their service locations/payment locations to the POS paymentsystem, the distinct payment code information for each distinct paymentlocation may therefore be associated with the service location and/orthe seller of that payment location. While a few examples have beenprovided, one of skill in the art will recognize that payment codeinformation may be associated, mapped, and/or otherwise related withpayment information for payment locations in a database in a variety ofother scenarios while remaining within the scope of the presentdisclosure.

In an embodiment, payment information for a payment location may includea number of details about the payment location such as, for example, anidentifier for payment location (e.g., that allows the payment locationto be distinguished from other payment locations in the servicelocation), a cost for the payment location, any payment variablesassociated with the cost of the payment location (e.g., a payment ratethat is a function of the amount of time the payment location is used),and/or a variety of other payment location information known in the art.The seller or POS payment system provider may enter the paymentinformation for the payment locations of a service location into adatabase (e.g., using a web interface, through an ApplicationProgramming Interface (API), and/or using a variety of other methodsknown in the art) and relate, map, and/or other associate each distinctset of that payment information (i.e., payment information for aparticular payment location) with distinct payment code information(which may be generated using methods known in the art). The paymentinformation may also include the name of the seller, seller accountinformation, seller contact information, a payment location description,etc.

The method 100 then proceeds to block 106 where the payment codeinformation is sent to the seller. As discussed above, payment codeinformation may include an alphanumeric character string and/or otheridentifier that may be generated using methods known in the art. Thepayment code information may be sent to a seller device and used by aseller to create a sign, a sticker, a tag, a card, a label, a magnet, adecal, and/or or other physical representation that includes the paymentcode information. For example, the payment code information may be usedto create a sign that may include, for example, a Universal Product Code(UPC), an International Article Number (EAN), a Quick Response (QR)code, and/or a variety of other identifiers known in the art. Then, inan embodiment, at block 106, the payment code information associatedwith the payment information at block 104 of the method is sent to theseller device, and a sign may be created that includes the payment codeinformation and that is located adjacent the payment location. Forexample, FIG. 2 illustrates a plurality of a signs 206, with each sign206 located adjacent to and associated with a respective paymentlocation 202 in the service location 200. While a few examples ofpayment code information are provided below, one of skill in the artwill recognize that a variety of different payment code information willfall within the scope of the present disclosure.

Referring now to FIGS. 1, 2, and 3, the method 100 then proceeds toblock 108 where payment code information is received from a payer. Inthe embodiment discussed below, a payer having a mobile payer device 300such as, for example, a phone or other mobile computing device, entersthe service location 200 of FIG. 2 and decides to pay for one of thepayment locations 202. However, this embodiment is presented only as anexample, and one of skill in the art will recognize that variety ofother POS payment scenarios will fall within the scope of the presentdisclosure. At block 108, upon deciding to purchase one of the paymentlocations 202, the payer may use their payer device 300 to start a payerapplication that is included on the payer device 300. In an embodiment,the payer application includes instructions that are stored on anon-transitory, computer-readable medium that, when executed by aprocessor in the payer device, cause the processor to perform thefunctions of the payment application discussed below. The paymentapplication may be provided by the operator of the POS payment system(e.g., a seller that operates the POS payment system, a POS paymentsystem provider that operates the POS payment system for a plurality ofsellers, etc.)

Activation of the payment application provides a payment codeinformation provision page through the payment application on the payerdevice 300. FIG. 3 illustrates a payer device 300 that includes adisplay 302 displaying a payment code information provision page 304.The payment code information provision page 304 includes a first paymentcode information acquisition section 306 and a second payment codeinformation acquisition section 308. In the illustrated embodiment, thefirst payment code information acquisition section 306 provides for the‘scanning’, ‘visual’, or ‘image’ acquisition of payment codeinformation, while the second payment code information acquisitionsection 308 provides for the ‘manual’, ‘text’, or otherwise more userintensive acquisition of payment tag information, as discussed infurther detail below. The first payment code information acquisitionsection 306 includes an image capture window 306 a, and the secondpayment code information acquisition section 308 includes a text input308 a.

FIG. 4 illustrates a user 400 using the payer device 300 to providepayment code information 402 that is located on the sign 206 in order topay for a parking space 202 for a car 404. As can be seen in FIG. 4, inresponse to entering the service area 200, described above withreference to FIG. 2, and deciding to use the parking space 202, the user400 has parked the car 404 in the parking space 202, started the paymentapplication on the payer device 300, and is using the payment codeinformation provision page 304 on the payer device 300 to capture thepayment code information 402 using the payment application 304.

In the embodiment illustrated in FIG. 5, payment code information 500,which may be the payment code information 402 illustrated in FIG. 4,includes a UPC. The payer device 300 may include a camera that isoperable to capture an image of the payment code information 500 and,using methods known in the art, the payment application may use theimage to determine details of the payment code information 500 (e.g.,the information encoded in the UPC). In another example, the payerdevice 300 may include a scanning device that is operable to provide alight source on the payment code information 500 and measure theintensity of the light reflected back, and the payment application mayuse the measured light intensities to determine the details of thepayment tag information 500 using methods known in the art. In anotherembodiment, the payment code information 500 may include human-readableinformation (e.g., “4815162342” on the payment code information 500 inthe illustrated embodiment) that the payer 400 may enter into the textinput 308 a in the second payment code information acquisition section308, and the payment application may use the text string as the paymentcode information. In the embodiment illustrated in FIG. 6, payment codeinformation 600, which may be the payment code information 402illustrated in FIG. 4, includes a QR code. The payer device 300 mayinclude a camera that is operable to capture an image of the paymentcode information 600 and, using methods known in the art, the paymentapplication may use the image to determine the details of the paymentcode information 600 (e.g., the information encoded in the QR code).

The method 100 then proceeds to block 108 where payment code informationis received from a payer. Upon capturing and/or determining the paymentcode information in block 106 of the method 100, the payment applicationsends the payment code information over a network to a paymentinformation engine provided by an operator of the POS payment system.Thus, the operator of the POS payment system receives the payment codeinformation. The method 100 then proceeds to block 110 where paymentinformation is retrieved using the payment code information. Uponreceiving the payment code information from the payer, the paymentinformation engine then accesses a payment information databases anduses that payment code information to determine the payment informationthat is associated with that payment code information and paymentlocation 202. In addition to the payment code information, the payerdevice may send information that identifies the payer device, the payer,the date and time of the transaction, etc.

Referring now to FIGS. 1 and 7, the method 100 then proceeds to block112 where the payment information is sent to the payer. Upon retrievingthe payment information, the payment information retrieval engine sendsthat payment information over the network to the payment application onthe payer device 300. FIG. 7 includes illustrates the payer device 300displaying (e.g., on the display 302), a payment information page 700that includes the payment information associated with the payment codeinformation sent in block 108 and received from the operator of the POSpayment system in block 112. In the illustrated embodiment, the paymentinformation page 700 includes a payment modifier 702, a payment total704, a service location graphic 706, a payment location graphic 706 a,and a payment confirmation indicator 708. As will be understood by oneof skill in the art, the payer may use the payer device 300 to select,modify, or otherwise provide the payment modifier 702 (e.g., a time thatthe payment location/parking space will be used), and the payment total704 will adjust based on the payment rate for the payment location. Theservice location graphic 706 provides the payer the layout of theservice location and the payment location graphic 706 a indicates to thepayer which payment location in the service location the payer is aboutto pay for.

While one embodiment of the payment information page has beenillustrated, one of skill in the art will recognize that a wide varietyof changes to the payment information page will fall within the scope ofthe present disclosure. For example, using the parking services exampledescribed above, the payer may be given an option to authorize a paymentfor an undetermined amount of time (e.g., the payer will be charged forhowever long the car is parked in the parking space/payment location.)In another example, the payer may be allowed to move the paymentlocation graphic 706 a to different locations in the service locationgraphic in the event the payment location graphic 706 a is incorrectlypositioned (e.g., the user has captured the wrong payment codeinformation relative to the payment location at which their car isparked.)

The method 100 then proceeds to block 114 where payment confirmation isreceived from the payer. Upon determining that the information on thepayment information page 700 is accurate (e.g., the payment modifier iscorrect, the payment location graphic 706 a is in the correct positionin the service location graphic 706, etc.), the payer may select thepayment confirmation indicator 708 in order to send a paymentconfirmation to a payer account engine used by the operator of the POSpayment system. In an embodiment, the payer may have previouslyassociated a payer account with the payment application such that thesending of the payment confirmation includes payer account informationfor the payer account of the payer. In another embodiment, the payeraccount of the payer may be associated with the payment application, butthe payer may be prompted (e.g., upon selecting the payment confirmationindicator 708) to provide security credentials for the payer accountsuch that the sending of the payment confirmation to the payment accountengine includes payer account information for the payer account of thepayer. In yet another embodiment, there may be no payer accountassociated with the payment application, and upon selection of thepayment confirmation indicator 708, the payer may be redirected to apayer account page (not illustrated) that requests security credentialsand allows the payer to use a payer account to make a payment.

The method 100 then proceeds to block 116 where a payment is initiatedfrom the payer to the seller. Upon receiving the payment confirmationfrom the payer in block 114, the payment account engine may use selleraccount information that may have been included in the paymentinformation associated with the payment code information, payer accountinformation that may have been received along with the paymentconfirmation as discussed above, and the payment confirmation toinitiate a payment from the payer to the seller. In one embodiment, thepayer account and seller account are provided by a payment serviceprovider such as, for example, PayPal, Inc. of San Jose, Calif., and thepayment service provider is the operator of the POS payment system suchthat the a payment may be made from the payer account to the selleraccount upon receiving the payment confirmation in block 114. In anotherembodiment, the seller is the operator of the POS payment system, andthe seller must then send the seller account information, the payeraccount information, and the payment confirmation to the payer accountprovider of the payer (e.g., a payment service provider, a fundingaccount provider, etc.) such that a payment may be made from the payeraccount to the seller account. While a few examples have been providedof payments being made from a payer account to a seller account, one ofskill in the art will recognize that a wide variety of payments andentities may be involved in the payment transfer been the payer accountand the seller account while remaining within the scope of the presentdisclosure.

Referring now to FIGS. 1 and 8, the method 100 then proceeds to block118 where payment information and an indication of payment confirmationare sent to the seller. The operator of the POS payment system, inresponse to receiving the payment confirmation in block 114, may sendthe seller (e.g., the seller device and/or other POS device at theservice location) the payment information received with the paymentconfirmation, along with an indicator that the payer has confirmed thepayment and/or that a payment has been initiated and/or that a paymenthas been completed between the payer account and the seller account.FIG. 8 illustrates a seller device 800 displaying a service locationmonitoring page 804 that may be provided with the payment informationprovided to the seller. The service location monitoring page 804includes a service location graphic 806 that includes the paymentlocations along with payer graphics 808 in the occupied paymentlocations. The service location monitoring page 804 may provide anattendant with a variety of functionality such as, for example, paidtime left indicators 810 that may be provided when the attendant selectsone of the payer graphics 808 on the service location monitoring page804. Other indicators may be provided as well, such as the time expiredindicators (e.g., the X's over the payer graphics 808) that indicatethat the payment locations are being occupied but are no longer paidfor. Thus, the seller may use the seller device to manage and trackpayments for the payment locations at the service location. In anembodiment, a payment confirmation or receipt may be sent to the payeron the payer device in response to the initiation and/or completion ofthe payment to the seller. While a few examples have been provided offunctionality for a service location monitoring page 804, one of skillin the art will recognize that a wide variety of functionality willremain within the scope of the present disclosure.

Thus, a system and method have been described that allow a seller to use“dumb” point of sale signs for use with ‘smart’ payer devices such thatpayers can pay for parking services provided by the seller. The ‘dumb’point of sale signs are cheap and easy to maintain, eliminate the needfor the seller to provide a ‘smart’ POS device to receive or processpayments, and simply require the payer to use their ‘smart’ phones inorder to pay the seller for use of their parking services. In addition,in some embodiments in which the seller is not the operator of the POSpayment system (e.g., when a trusted third party provider operates thePOS payment system), the payer need not provide sensitive informationdirectly to the seller in order to complete the purchase.

Referring now to FIGS. 1 and 9, another embodiment of the method 100 forpoint of sale (POS) payments is illustrated. The method 100 begins atblock 102 where payment information is received from a seller. Forexample, referring to FIG. 9, a seller may operate a service location900 that, in the illustrated embodiment, includes a train. The servicelocation 900 includes a plurality of payment locations 902 that, in theillustrated embodiment, include seats on the train. In the embodimentillustrated in FIG. 9, a plurality of payers have paid for respectivepayment locations 902 (e.g., in the illustrated embodiment, the darkenedpayment locations 902 may correspond to train seats 902 that have beenpaid for by payers) in order to use the payment locations 902 duringtravel on the train. In one example, at block 102, the seller may use aseller device to send payment information that is associated with thepayment locations 902 in the service location 900 to a paymentinformation engine, described in detail below. In another example, a POSpayment system provider may include a payment code engine that acceptspayment information for payment locations in service locations from aplurality of different sellers. In this example, the payment informationmay include additional information that is not directly related to thepayment location such as, for example, seller information about theseller.

The method 100 then proceeds to block 104 where the payment informationis associated with the payment code information substantially asdescribed above, and block 106 where the payment code information issent to the seller substantially as described above. The method 100 thenproceeds to block 108 where payment code information is received from apayer. Referring now to FIG. 10, a payer device 1000 is illustrated thatis similar to the payer device 300, described above, but with a paymentapplication displaying a payment code information provision page 1004 onthe display 1002 of the payer device 1000. In the embodiment illustratedin FIG. 10, the payment application is ‘tailored’ to the servicelocation 900 and includes a first payment information acquisitionsection 1006 with an image capture window 1006 a and a second paymentcode information acquisition section 1008 with a text input 1008 a thatoperating substantially similarly to the first payment code informationacquisition section 306, image capture window 306 a, second payment codeinformation acquisition section 308, and text input 308 a describedabove with reference to FIG. 3.

FIG. 11 illustrates a payer 1100 capturing payment code information 1102posted in one of the payment locations 902. As can be seen, the sellerhas provided payment code information 1102 on each of the paymentlocations 902 (train seats) in the service location 900 (train). Thepayer 1100 has decided to purchase one of the payment locations and, inresponse, is capturing an image of the payment code information 1102that is posted on that payment location 902 (in the illustratedembodiment, a sign located on the head rest of the train seat.) Whilethe payment code information 902 has been illustrated as being providedon the head rests of the train seats, the payment code information maybe provided in a variety of other locations such as, for example, on theseatback in front of the seat, on the floor, on an armrest, or in avariety of other locations adjacent the train seat. The payment codeinformation 1102 may then be sent to the operator of the POS paymentsystem substantially as discussed above.

The method 100 then proceeds to block 110 where the payment informationis retrieved using the payment code information substantially asdescribed above. Referring now to FIG. 12, at block 112 the paymentinformation is sent to the payer and may be used to provide a paymentinformation page 1200. The payment information page 1200 includes apayment modifier 1202 that, in the illustrated embodiment, allow thepayer to select, modify, or otherwise indicate a destination to whichthe payer wishes to travel. A payment total 1203 provides a totalpayment amount that may be adjusted depending on the destinationincluded in the payment modifier 1202. A service location graphic 1204is provided on the payment information page 1200 that illustrates theservice location 900 and includes a payment location indicator 1204 athat indicates which payment location 902 in the service location 900the payer is paying for. A payment confirmation indicator 1206 isprovided on the payment information page 1200 and operates insubstantially the same manner as the payment confirmation indicatordiscussed above. Thus, the payer may provide details such as adestination and a payment location, and then select the paymentconfirmation indicator 1206 in order to send the payment confirmation inblock 114. In other embodiments, payment modifiers on the paymentinformation page 1200 may include upgrades or options such as, forexample, food or beverage orders.

In other embodiments of the train service location 900 discussed above,a wide variety of modifications are envisioned as falling within thescope of the present disclosure. For example, a location determinationdevice such as a Global Positioning System (GPS) may be used todetermine the distance traveled by the payer device and, hence, thepayer. Thus, the payer may authorize a payment using the payment codeinformation and payment information discussed above, and the POS paymentsystem may determine the amount of the payment by determining thedistance traveled by the payer (e.g., the payment amount may becalculated in response to detection of the payer device leaving thetrain 900.) In another embodiment, the payer may purchase a specificpayment location 902, and then move within the service location 900 to adifferent payment location 902, and the payment application may allowthe payer to change the payment location 902 associated with the paymentsuch that it reflects the payment location 902 to which the payer hasmoved. In yet another embodiment, proof of payment may be provided tothe payer device (e.g., a receipt or other identifier) such that thepayer may move around the service location while still having proof thatthey have paid for one of the payment locations.

Upon receiving the payment confirmation from the payer in block 114, themethod 100 proceeds to block 116 where a payment is initiated from thepayer to the seller substantially as described above. The method thenproceeds to block 118 where the payment information and the indicationof the payment confirmation is sent to the seller substantially asdescribed above. FIG. 13 includes a seller device 1300 including adisplay 1302 that displays a service location monitoring page 1304. Theservice location monitoring page 1304 includes a service locationgraphic 1306 that includes payment location graphics that include openseats 1308 a and purchased seats 1308 b, with the purchased seats 1308 bgrayed out relative to the open seats 1308 a. As can be seen, anattendant may use the seller device 1300 to select a purchased seat inorder to be presented with a destination indicator 1310 that indicatesthe destination that was paid for in the purchase of that purchasedseat. In other embodiments, the destination indicator may show a varietyof other information such as, for example, a payer name.

In another example, a second payer may attempt to purchase a previouslypurchased payment location by sending the payment code information usingtheir payer device according to the method 100 above. In such anexample, the payment information engine may determine that the paymentcode information received from the second payer is already associatedwith the payment for that payment location and, thus, the paymentlocation is ‘taken’. In such a situation, the payment information enginemay provide to the payer device of the second payer a declined paymentindicator that may indicate that the payment location has been purchasedand that the second payer much purchase a different payment location.

Thus, another embodiment of a system and method have been described thatallow a seller to use “dumb” point of sale signs for use with smartpayer devices such that payers can pay for transportation servicesprovided by the seller. The ‘dumb’ point of sale signs are cheap andeasy to maintain, and simply require the payer to use their ‘smart’phones in order to pay the seller for use of their transportationservices.

As discussed above, a wide variety of embodiments of the POS paymentsystem other than the parking services and transportation services,illustrated and described above, are envisioned as falling within thescope of the present disclosure. For example, the POS payment system maybe implemented in a restaurant. In one embodiment, a restaurant (servicelocation) may include a plurality of tables (payment locations), andpayment code information may be provided at each table. Thus, a servermay charge food and drinks to the table, and the payer may pay for thebill at any time using their payer device to capture the payment codeinformation, review the bill (payment information), and provide apayment according to the method 100 above. Furthermore, the server orrestaurant owner may review the tables that have paid using the sellerdevices and service location monitoring pages discussed above.

In another embodiment, a restaurant such as, for example, a fast foodrestaurant, may include a menu in which each food or drink item isassociated with payment code information. The user may then capture thepayment code information for each of the food and/or drink items theywish to purchase, and pay for those food and drink items according tothe method 100 discussed above. Payment modifiers may be provided duringthe method 100 to allow the payer to modify the food and/or drink itemsaccording to the desires of the payer, including amounts/quantities,desired features, etc.

In a further embodiment, the POS payment system may be implemented inretail stores (e.g., payment code information may be associated withclothing articles), gyms, spas, offices, theaters, concert halls, and/ora variety of other businesses known in the art.

Referring now to FIG. 14, an embodiment of a networked system 1400 usedin the POS payment system described above is illustrated. The networkedsystem 1400 may include any or all of a plurality of payer devices 1402,a plurality of seller devices 1404, a payment service provider device1406, a plurality of funding account holder devices 1408, and/or a POSpayment system provider device 14110 in communication over a network1412. Any of the payer devices 1402 may be the payer devices 300 and/or1000 discussed above. The seller devices 1404 may be the seller devices800 and/or 1300 operated by the sellers of the service locationsdiscussed above. The payment service provider device 1406 may beoperated by a payment service provider such as, for example, PayPal Inc.of San Jose, Calif., as discussed above. The funding account providerdevices 1408 may be funding account provider devices operated by fundingaccount providers such as, for example, credit card account providers,bank account providers, savings account providers, and a variety ofother account providers known in the art. The POS payment systemprovider device 1410 may be operated by a POS payment system provider asdiscussed above. One of skill in the art will recognize that some of thedevices in the networked system 1400 may not be necessary in differentembodiments. For example, where the POS payment system is provided by aseller, the POS payment system provider device 1410 and/or the paymentservice provider device 1406 may not be included in the networked system1400. In another example, where the online payment system is provided bya payment service provider device 1406, the POS payment system providerdevice 1410 may not be included in the networked system 1400. In anotherexample, where the online payment system is provided by a fundingaccount provider device 1408, the online payment system provider device1410 and the payment service provider device 1406 may not be included inthe networked system 1400. Thus, one of skill in the art will recognizethat a variety of modifications may be provided to the networked system1400 while remaining within the scope of the present disclosure.

The payer devices 1402, seller devices 1404, payment service providerdevice 1406, funding account provider devices 1408, and/or the POSpayment service provider device 1410 may each include one or moreprocessors, memories, and other appropriate components for executinginstructions such as program code and/or data stored on one or morecomputer readable mediums to implement the various applications, data,and steps described herein. For example, such instructions may be storedin one or more computer readable mediums such as memories or datastorage devices internal and/or external to various components of thesystem 1400, and/or accessible over the network 1412.

The network 1412 may be implemented as a single network or a combinationof multiple networks. For example, in various embodiments, the network1412 may include the Internet and/or one or more intranets, landlinenetworks, wireless networks, and/or other appropriate types of networks.

The payer devices 1402 may be implemented using any appropriatecombination of hardware and/or software configured for wired and/orwireless communication over network 1412. For example, in oneembodiment, the payer devices 1402 may be implemented as a personalcomputer of a user in communication with the Internet. In otherembodiments, the payer devices 1402 may be a smart phone, personaldigital assistant (PDA), laptop computer, and/or other types ofcomputing devices.

The payer devices 1402 may include one or more browser applicationswhich may be used, for example, to provide a convenient interface topermit the payer to browse information available over the network 1412.For example, in one embodiment, the browser application may beimplemented as a web browser configured to view information availableover the Internet.

The payer devices 1402 may also include one or more toolbar applicationswhich may be used, for example, to provide user-side processing forperforming desired tasks in response to operations selected by thepayer. In one embodiment, the toolbar application may display a userinterface in connection with the browser application. In anotherembodiment, the toolbar application may provide the payment application,discussed above.

The payer devices 1402 may further include other applications as may bedesired in particular embodiments to provide desired features to thepayer devices 1402. In particular, the other applications may includethe payment application, discussed above, for payments assisted by apayment service provider through the payment service provider device1406. The other applications may also include security applications forimplementing user-side security features, programmatic user applicationsfor interfacing with appropriate application programming interfaces(APIs) over the network 1412, or other types of applications. Emailand/or text applications may also be included, which allow the payer tosend and receive emails and/or text messages through the network 1412.The payer devices 1402 include one or more user and/or deviceidentifiers which may be implemented, for example, as operating systemregistry entries, cookies associated with the browser application,identifiers associated with hardware of the payer devices 1402, or otherappropriate identifiers, such as a phone number. In one embodiment, theuser identifier may be used by the payment service provider device 1406,funding account provider devices 1408, and/or online payment serviceprovider device 1410 to associate the user with a particular account asfurther described herein.

The seller devices 1404 may be maintained, for example, by the seller ofthe product, a conventional or on-line merchant, conventional or digitalgoods seller, individual seller, and/or application developer offeringvarious products and/or services in exchange for payment to be receivedconventionally or over the network 1412. In this regard, the sellerdevices 1404 may include a database identifying available productsand/or services which may be made available for viewing and purchase bythe payer. In addition, databases identifying available products and/orservices will be available to any provider of the online payment system,as discussed above.

Referring now to FIG. 15, an embodiment of a payer device 1500 isillustrated. The payer device 1500 may be the payer devices 300, 1000,and/or 1402. The payer device 1500 includes a chassis 1502 having adisplay 1504 and an input device including the display 1504 and aplurality of input buttons 1506. One of skill in the art will recognizethat the payer device 1500 is a portable or mobile phone including atouch screen input device and a plurality of input buttons that allowthe functionality discussed above with reference to the method 100.However, a variety of other portable/mobile payer devices may be used inthe method 100 without departing from the scope of the presentdisclosure.

Referring now to FIG. 16, an embodiment of a computer system 1600suitable for implementing, for example, the payer devices 300, 1000,1402, and/or 1500, the seller devices 800, 1300, and/or 1404, thepayment service provider device 1406, the funding account providerdevices 1408, and/or the POS payment service provider device 1410 isillustrated. It should be appreciated that other devices utilized bypayers, sellers, payment service providers, funding account providers,and/or online payment service providers in the payment system discussedabove may be implemented as the computer system 1600 in a manner asfollows.

In accordance with various embodiments of the present disclosure,computer system 1600, such as a computer and/or a network server,includes a bus 1602 or other communication mechanism for communicatinginformation, which interconnects subsystems and components, such as aprocessing component 1604 (e.g., processor, micro-controller, digitalsignal processor (DSP), etc.), a system memory component 1606 (e.g.,RAM), a static storage component 1608 (e.g., ROM), a disk drivecomponent 1610 (e.g., magnetic or optical), a network interfacecomponent 1612 (e.g., modem or Ethernet card), a display component 1614(e.g., CRT or LCD), an input component 1618 (e.g., keyboard, keypad, orvirtual keyboard), a cursor control component 1620 (e.g., mouse,pointer, or trackball), a camera component 1622, and/or a locationdetermination device 1623 (e.g., a Global Positioning System (GPS)device as illustrated, a cell tower triangulation device, and/or avariety of other location determination devices known in the art.) Inone implementation, the disk drive component 1610 may comprise adatabase having one or more disk drive components.

In accordance with embodiments of the present disclosure, the computersystem 1600 performs specific operations by the processor 1604 executingone or more sequences of instructions contained in the memory component1606, such as described herein with respect to the payer devices 300,1000, 1402, and 1500, the seller devices 800, 1300, and 1404, thepayment service provider device 1406, the funding account providerdevices 1408, and/or the POS payment service provider device 1410. Suchinstructions may be read into the system memory component 1606 fromanother computer readable medium, such as the static storage component1608 or the disk drive component 1610. In other embodiments, hard-wiredcircuitry may be used in place of or in combination with softwareinstructions to implement the present disclosure.

Logic may be encoded in a computer readable medium, which may refer toany medium that participates in providing instructions to the processor1604 for execution. Such a medium may take many forms, including but notlimited to, non-volatile media, volatile media, and transmission media.In one embodiment, the computer readable medium is non-transitory. Invarious implementations, non-volatile media includes optical or magneticdisks, such as the disk drive component 1610, volatile media includesdynamic memory, such as the system memory component 1606, andtransmission media includes coaxial cables, copper wire, and fiberoptics, including wires that comprise the bus 1602. In one example,transmission media may take the form of acoustic or light waves, such asthose generated during radio wave and infrared data communications.

Some common forms of computer readable media includes, for example,floppy disk, flexible disk, hard disk, magnetic tape, any other magneticmedium, CD-ROM, any other optical medium, punch cards, paper tape, anyother physical medium with patterns of holes, RAM, PROM, EPROM,FLASH-EPROM, any other memory chip or cartridge, carrier wave, or anyother medium from which a computer is adapted to read. In oneembodiment, the computer readable media is non-transitory.

In various embodiments of the present disclosure, execution ofinstruction sequences to practice the present disclosure may beperformed by the computer system 1600. In various other embodiments ofthe present disclosure, a plurality of the computer systems 1600 coupledby a communication link 1624 to the network 1412 (e.g., such as a LAN,WLAN, PTSN, and/or various other wired or wireless networks, includingtelecommunications, mobile, and cellular phone networks) may performinstruction sequences to practice the present disclosure in coordinationwith one another.

The computer system 1600 may transmit and receive messages, data,information and instructions, including one or more programs (i.e.,application code) through the communication link 1624 and the networkinterface component 1612. The network interface component 1612 mayinclude an antenna, either separate or integrated, to enabletransmission and reception via the communication link 1624. Receivedprogram code may be executed by processor 1604 as received and/or storedin disk drive component 1610 or some other non-volatile storagecomponent for execution.

Referring now to FIG. 17, an embodiment of a payment serviceprovider/seller/POS payment service provider/funding account providerdevice 1700 is illustrated (i.e., the device 1700 may be any orcombinations of the payment service provider device, the seller device,the POS payment service provider device, and/or the funding accountprovider device, depending on the embodiment and which entity orentities are providing the online payment system). The device 1700includes a communication engine 1702 that is coupled to the network1412, a payment information engine 1704, and a payer account engine1706. The payment information engine 1704 is coupled to the payeraccount engine 1406 and a payment information database 1708, and thepayer account engine 1706 is coupled to the payment information engine1704 and a payer account database 1710. The communication engine 1702may be software or instructions stored on a computer-readable mediumthat allows the device(s) 1700 to send and receive information over thenetwork 1412. The payment information engine 1704 may be software orinstructions stored on a computer-readable medium that is operable toreceive payment information or payment code information, associatepayment information with payment code information, retrieve productinformation from the payment information database 1706, and provide thepayment information to the communication engine 1702 (e.g., fortransmittal to the payer device) and/or the payer account engine 1706.The payer account engine 1706 may be software or instructions stored ona computer-readable medium that is operable to receive payer accountcredentials, retrieve payer account information from the payer accountdatabase 1710, receive payment information from the payment informationengine 1704, and provide payer account information to the communicationengine 1702 (e.g., for transmittal to the payer device). While theengines 1702, 1704, and 1706 and the databases 1708 and 1710 have beenillustrated as located in the device 1700, one of skill in the art willrecognize that they may be connected to one another through the network1412 (e.g., when the online payment system is provided by more than oneentity such as, for example, when the payer account engine is providedby a funding account provider and the product retrieval engine isprovided by a seller) without departing from the scope of the presentdisclosure.

Where applicable, various embodiments provided by the present disclosuremay be implemented using hardware, software, or combinations of hardwareand software. Also, where applicable, the various hardware componentsand/or software components set forth herein may be combined intocomposite components comprising software, hardware, and/or both withoutdeparting from the scope of the present disclosure. Where applicable,the various hardware components and/or software components set forthherein may be separated into sub-components comprising software,hardware, or both without departing from the scope of the presentdisclosure. In addition, where applicable, it is contemplated thatsoftware components may be implemented as hardware components andvice-versa.

Software, in accordance with the present disclosure, such as programcode and/or data, may be stored on one or more computer readablemediums. It is also contemplated that software identified herein may beimplemented using one or more general purpose or specific purposecomputers and/or computer systems, networked and/or otherwise. Whereapplicable, the ordering of various steps described herein may bechanged, combined into composite steps, and/or separated into sub-stepsto provide features described herein.

The foregoing disclosure is not intended to limit the present disclosureto the precise forms or particular fields of use disclosed. As such, itis contemplated that various alternate embodiments and/or modificationsto the present disclosure, whether explicitly described or impliedherein, are possible in light of the disclosure. For example, the aboveembodiments have focused on sellers and payers; however, a payer orconsumer can pay, or otherwise interact with any type of recipient,including charities and individuals. The payment does not have toinvolve a purchase, but may be a loan, a charitable contribution, agift, etc. Thus, seller as used herein can also include charities,individuals, and any other entity or person receiving a payment from apayer. Having thus described embodiments of the present disclosure,persons of ordinary skill in the art will recognize that changes may bemade in form and detail without departing from the scope of the presentdisclosure. Thus, the present disclosure is limited only by the claims.

What is claimed is:
 1. A system for point of sale payments, comprising:a service location that includes a plurality of payment locations andrespective payment code information displayed adjacent each of theplurality of payment locations; and a seller device that is associatedwith the service location and a seller, wherein the seller device islocated at the service location, coupled to a network, and includes: amemory storing a plurality of payment information that is associatedwith the seller and the service location; a display device; and aprocessor coupled to the memory and the display device, wherein theprocessor is configured to cause the seller device to perform operationscomprising: receiving, from a first payer device wirelessly over thenetwork, payment code information associated with a first paymentlocation of the plurality of payment locations in the service location;retrieving first payment information from the plurality of paymentinformation from the memory using the payment code information;providing, to the first payer device wirelessly over the network, thefirst payment information in a payment information graphical userinterface that includes a payer service location graphic that provides alayout of the service location including relative locations of each ofthe plurality of payment locations, and a payment location graphic thatis located in the payer service location graphic and that indicates arelative location, from the relative locations of each of the pluralityof payment locations in the service location, of the first paymentlocation associated with the payment code information; receiving, fromthe first payer device wirelessly over the network in response to atleast one input received through the payment information graphical userinterface provided on the first payer device, a payment location graphicadjustment that moves the payment location graphic to a differentlocation in the payer service location graphic to provide a request topay for a second payment location of the plurality of payment locationsinstead of the first payment location, along with a payment confirmationand, in response, initiating a payment from a payer account associatedwith the payer device to a seller account included in the paymentinformation and sending the payment information and an indication of thepayment confirmation to the seller device over the network; andproviding, for display on the display device, a service locationmonitoring page that includes a seller service location graphicillustrating the service location and the plurality of paymentlocations, wherein the service location monitoring page provides acurrent, real-time payment location status of the plurality of paymentlocations in the service location by providing payer graphics in paymentlocations in the service location that have been paid for and indicatingthe payment locations in the service location that have not been paidfor.
 2. The system of claim 1, wherein the payment code informationassociated with a first payment location is provided on a sign forcapture by the first payer device at the service location.
 3. The systemof claim 1, wherein the processor is further configured to cause theseller device to perform operations comprising: providing, for displayon the display device, a first payer graphic of the payer graphics inthe seller service location graphic that indicates the relative locationin the service location of the second payment location in response toreceiving the payment location graphic adjustment and the paymentconfirmation.
 4. The system of claim 1, wherein the processor is furtherconfigured to cause the seller device to perform operations comprising:determining a payment time associated with the payment information; andcalculating the payment using the payment time.
 5. The system of claim1, wherein the processor is further configured to cause the sellerdevice to perform operations comprising: receiving, from a second payerdevice over the network, the payment code information associated withthe second payment location; determining that the payment codeinformation is associated with the payment initiated by the payerdevice; and sending, to the second payer device over the network, adeclined payment indicator.
 6. The system of claim 3, wherein theprocessor is further configured to cause the seller device to performoperations comprising: receiving a selection on the service locationmonitoring page of the first payer graphic in the second paymentlocation in the service location that has been paid for; and providing,for display on the display device, at least one of a payment time and apayment destination associated with the second payment location.
 7. Anon-transitory machine-readable medium having stored thereonmachine-readable instructions executable to cause a machine to performoperations comprising: receiving, from a payer device wirelessly over anetwork, payment code information associated with a first paymentlocation of a plurality of payment locations in a service locationassociated with a seller device operated by a seller; retrieving, from adatabase, payment information that is also associated with the paymentcode information; providing, to the payer device wirelessly over thenetwork, the payment information in a payment information graphical userinterface that includes a payer service location graphic that provides alayout of the service location including relative locations of each ofthe plurality of payment locations, and a payment location graphic thatis located in the payer service location graphic and that indicates arelative location of the relative locations in the service location ofthe first payment location associated with the payment code information;receiving, from the payer device wirelessly over the network in responseto at least one input received through the payment information graphicaluser interface provided on the first payer device, a payment locationgraphic adjustment that moves the payment location graphic to adifferent location in the payer service location graphic to provide arequest to pay for a second payment location of the plurality of paymentlocations instead of the first payment location, along with a paymentconfirmation and, in response, initiating a payment from a payer accountassociated with the payer device to a seller account included in thepayment information and sending the payment information and anindication of the payment confirmation to the seller device over thenetwork and providing, for display on the seller device, a servicelocation monitoring page that includes a seller service location graphicillustrating the service location and the plurality of paymentlocations, wherein the service location monitoring page provides acurrent, real-time payment location status of the plurality of paymentlocations in the service location by providing payer graphics in thepayment locations in the service location that have been paid for andindicating the payment locations in the service location that have notbeen paid for.
 8. The non-transitory machine-readable medium of claim 7,wherein the payment code information is provided for capture by thepayer device at the service location and transmission by the payerdevice over the network.
 9. The non-transitory machine-readable mediumof claim 8, wherein the payment code information is provided for captureby a camera on the payer device.
 10. The non-transitory machine-readablemedium of claim 7, wherein the operations further comprise: providing afirst payer graphic of the payer graphics on the seller service locationgraphic that indicates the relative location in the service location ofthe second payment location in response to receiving the paymentlocation graphic adjustment and the payment confirmation.
 11. Thenon-transitory machine-readable medium of claim 7, wherein theoperations further comprise: determining a payment time associated withthe payment instruction; and calculating the payment using the paymenttime.
 12. The non-transitory machine-readable medium of claim 7, whereinthe payment information includes a payment location and the operationsfurther comprise: receiving, from a secondary payer device over thenetwork, the payment code information associated with the paymentlocation; determining that the payment code information is associatedwith the payment initiated by the payer device; and sending, to thesecondary payer device over the network, a declined payment indicator.13. The non-transitory machine-readable medium of claim 7, wherein theoperations further comprise: receiving, from the seller device, aselection on the service location monitoring page of a first payergraphic in the first payment location in the service location that hasbeen paid for; and providing, for display on the seller device, at leastone of a payment time and a payment destination associated with thefirst payment location.
 14. A method for point of sale payments,comprising: receiving, from a payer device wirelessly over a network,payment code information associated with a first payment location of aplurality of payment locations in a service location associated with aseller device operated by a seller; retrieving, from a database, paymentinformation that is also associated with the payment code information;providing, to the payer device wirelessly over the network, the paymentinformation in a payment information graphical user interface thatincludes a payer service location graphic that provides a layout of theservice location including relative locations of each of the pluralityof payment locations, and a payment location graphic that is located inthe payer service location graphic and that indicates a relativelocation of the relative locations in the service location of the firstpayment location associated with the payment code information;receiving, from the payer device wirelessly over the network in responseto at least one input received through the payment information graphicaluser interface provided on the first payer device, a payment locationgraphic adjustment that moves the payment location graphic to adifferent location in the payer service location graphic to provide arequest to pay for a second payment location of the plurality of paymentlocations instead of the first payment location, along with a paymentconfirmation and, in response, initiating a payment from a payer accountassociate with the payer device to a seller account included in thepayment information and sending the payment information and anindication of the payment confirmation to the seller device over thenetwork; and providing, for display on the seller device, a servicelocation monitoring page that includes a seller service location graphicillustrating the service location and the plurality of paymentlocations, wherein the service location monitoring page provides acurrent, real-time payment location status of the plurality of paymentlocations in the service location by providing payer graphics in paymentlocations in the service location that have been paid for and indicatingthe payment locations in the service location that have not been paidfor.
 15. The method of claim 1, wherein the payment code information isprovided for capture by the payer device at the service location andtransmission by the payer device over the network.
 16. The method ofclaim 15, wherein the payment code information is provided for captureby a camera on the payer device.
 17. The method of claim 14, furthercomprising: providing a first payer graphic of the payer graphics in theseller service location graphic that indicates the relative location inthe service location of the second payment location in response toreceiving the payment location graphic adjustment and the paymentconfirmation.
 18. The method of claim 14, further comprising:determining a payment time associated with the payment information; andcalculating the payment using the payment time.
 19. The method of claim14, wherein the payment information includes a payment location and themethod further comprises: receiving, from a secondary payer device overthe network, the payment code information associated with the paymentlocation; determining that the payment code information is associatedwith the payment initiated by the payer device; and sending, to thesecondary payer device over the network, a declined payment indicator.20. The method of claim 14, further comprising: receiving, from theseller device, a selection on the service location monitoring page of afirst payer graphic in the first payment location in the servicelocation that has been paid for; and providing, for display on theseller device, at least one of a payment time and a payment destinationassociated with the first payment location.
 21. The system of claim 1,wherein the current, real-time payment location status of the pluralityof payment locations in the service location on service locationmonitoring page includes time expired indicators for each payer graphicon the seller service location graphic that is associated with a paymentlocation in the service location that is currently occupied but nolonger paid for.
 22. The non-transitory machine-readable medium of claim7, wherein the current, real-time payment location status of theplurality of payment locations in the service location on servicelocation monitoring page includes time expired indicators for each payergraphic on the seller service location graphic that is associated with apayment location in the service location that is currently occupied butno longer paid for.
 23. The method of claim 14, wherein the current,real-time payment location status of the plurality of payment locationsin the service location on service location monitoring page includestime expired indicators for each payer graphic on the seller servicelocation graphic that is associated with a payment location in theservice location that is currently occupied but no longer paid for.